Information processing apparatus, method of controlling the same, and  storage medium

ABSTRACT

There is provided with an information processing apparatus and a method of controlling the same. The apparatus sets a naming rule for an image file and determines whether or not the set naming rule satisfies a predetermined condition. If it is determined that the naming rule does not satisfy the predetermined condition, the information processing apparatus warns a user. On the other hand, if it is determined that the naming rule satisfies the predetermined condition, the information processing apparatus generates a file name of the image file in accordance with the set naming rule, and stores the image file with the file name.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention is related to an information processing apparatus,a method of controlling the same, and a storage medium.

2. Description of the Related Art

In a service using a fax, digitization of a fax document received by anMFP or by fax is performed using a scan function of the MFP or ascanner, and the fax document is stored on a file server, or the like.The MFP is an abbreviation of Multi Function Peripheral, and one exampleof this is an image forming apparatus having a plurality of functionssuch as those for a copying machine, a scanner, and a fax. In such acase, in order to allow for optimization of digitization and file serverstoring work, a received facsimile transfer system is constructed todigitize a fax document, and automatically store the document to a fileserver in accordance with attributes of the fax document. In this kindof system, a file name of a fax document that is received is generatedin accordance with a telephone number of a transmission source of thefax document, and other attribute information, and the fax document isstored to the file server. Here, if the file name is duplicated, a newfax document will overwrite an existing fax document, and so there isthe possibility of a fax document that was stored disappearing.

According to Japanese Patent Laid-Open No. 2002-64534, for example, atechnique of storing a fax document that the FAX server received, addinga unique identification number as the file name, is recited as astrategy for handling this kind of disappearance of a fax document thatis stored. If this technique is employed, an identification numberspecific to a communication network, or an identification numberspecific within a FAX server is used as the file name of the faxdocument, and thereby a unique file name can be generated, and data lossdue to duplication of the file name can be prevented.

However, with the technique recited in the above-described JapanesePatent Laid-Open No. 2002-64534, because the system side forcibly addsthe unique identification number as the file name, the visibility of theuser deteriorates. For this reason, there is the problem that when auser uses a fax document that is stored, it is difficult to identify adesired fax document, and the effort in searching for a desired documentis cumbersome.

SUMMARY OF THE INVENTION

An aspect of the present invention is to eliminate the above-mentionedproblems with conventional technology.

A feature of the present invention is to provide a technique by which itis possible to set so that a file name of an image file becomes unique,and so that a visibility for a user is enhanced.

According to a first aspect of the present invention, there is providedan information processing apparatus, comprising: a first setting unitconfigured to set a naming rule for an image file; a determination unitconfigured to determine whether or not the naming rule set by the firstsetting unit satisfies a predetermined condition; a warning unitconfigured to warn a user if it is determined by the determination unitthat the naming rule does not satisfy the predetermined condition; and acontrol unit configured to control so as to, if it is determined by thedetermination unit that the naming rule satisfies the predeterminedcondition, generate a file name of the image file in accordance with thenaming rule set by the first setting unit, and store the image file.

According to a second aspect of the present invention, there is provideda method of controlling an information processing apparatus operable tostore an image file, the method comprising: setting a naming rule for animage file; determining whether or not the naming rule set in thesetting satisfies a predetermined condition; warning a user if it isdetermined in the determining that the naming rule does not satisfy thepredetermined condition; and controlling so as to, if it is determinedin the determining that the naming rule satisfies the predeterminedcondition, generate a file name of the image file in accordance with thenaming rule set in the setting, and store the image file.

Further features of the present invention will become apparent from thefollowing description of exemplary embodiments with reference to theattached drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in and constitute apart of the specification, illustrate embodiments of the invention and,together with the description, serve to explain the principles of theinvention.

FIG. 1 depicts a view illustrating an example of an informationprocessing system according to a first embodiment of the presentinvention.

FIG. 2 is a block diagram for explaining a hardware configuration of anMFP according to the first embodiment.

FIG. 3 is a block diagram for showing a hardware configuration of a fileserver according to the first embodiment.

FIG. 4 is a functional block diagram for explaining a software moduleconfiguration of the MFP according to the first embodiment.

FIG. 5 is a functional block diagram for explaining a software moduleconfiguration of the file server according to the first embodiment.

FIG. 6 depicts a view illustrating an example of destination informationstored in a destination information management module of the MFPaccording to the first embodiment.

FIG. 7 depicts a view illustrating an example of a file storing transfersetting information stored in a transfer setting information managementmodule of the MFP according to the first embodiment.

FIG. 8 depicts a view illustrating an example of a status display screendisplayed on a console unit of the MFP according to the firstembodiment.

FIG. 9 depicts a view illustrating an example of a file server settingscreen that the MFP according to the first embodiment displays.

FIG. 10 depicts a view illustrating an example of a setting screen forsetting a file naming rule that the MFP according to the firstembodiment displays.

FIG. 11 depicts a view illustrating an example of a setting screen forsetting a folder naming rule that the MFP according to the firstembodiment displays.

FIG. 12 depicts a view illustrating an example of a transmission testscreen that the MFP according to the first embodiment displays.

FIG. 13 is a flowchart for describing file server setting, and filenaming rule and folder naming rule setting processing by the MFPaccording to the first embodiment.

FIG. 14 is a sequence diagram for describing processing in which the MFPaccording to the first embodiment receives image data in a fax, andtransfers an image file of the received image data to the file server.

FIG. 15 is a flowchart for describing fax reception processing by theMFP according to the first embodiment.

FIG. 16 is a flowchart for describing file name generation processing instep S1505 of FIG. 15 for an image file transferred.

FIG. 17 is a flowchart for describing folder name generation processingin step S1506 of FIG. 15 of the file server on which the image filetransferred is stored.

FIG. 18 is a flowchart for describing file naming rule settingprocessing of step S1306 in FIG. 13.

FIG. 19 depicts a view illustrating an example of a confirmation dialogdisplayed by the MFP according to a second embodiment of the presentinvention.

FIG. 20 is a flowchart for describing confirmation dialog displayprocessing by the MFP according to the second embodiment.

FIG. 21 depicts a view illustrating an example of transfer settinginformation according to the second embodiment.

FIG. 22 depicts a view illustrating an example of a folder naming rulesetting screen displayed by the MFP according to a third embodiment ofthe present invention.

DESCRIPTION OF THE EMBODIMENTS

Embodiments of the present invention will now be described hereinafterin detail, with reference to the accompanying drawings. It is to beunderstood that the following embodiments are not intended to limit theclaims of the present invention, and that not all of the combinations ofthe aspects that are described according to the following embodimentsare necessarily required with respect to the means to solve the problemsaccording to the present invention.

First Embodiment

Firstly, explanation will be given for a first embodiment according tothe present invention. In the first embodiment, explanation is given foran example of an MFP (multi-function peripheral) which is an example ofan image forming apparatus of the present invention, and fax documenttransfer setting processing, fax reception processing, and file transferprocessing in a system including a file server having a file storagefunction.

FIG. 1 depicts a view illustrating an overall configuration of aninformation processing system according to a first embodiment of thepresent invention.

In this information processing system, an MFP 110 and a file server 120are connected via a LAN 100.

The MFP 110 is a multi-function peripheral (a multifunction processingapparatus) having a console unit 111, a scanner unit 112, and a printerunit 113, and the MFP 110 is connected to a telephone public circuitnetwork 150 and can receive facsimiles. In the information processingsystem according to the first embodiment, the MFP 110 is used as areceiving terminal for fax documents. The file server 120 performsauthentication of connecting terminals, and stores and manages receivedfiles under a designated file name and folder name. However, the systemaccording to the first embodiment is not limited to the number ofdevices configured in FIG. 1. For example, by having the function of thefile server within the MFP 110, the MFP and the file server may beconfigured in the same apparatus. Also, the file server may beconfigured as a server on the Internet, or as a cloud system.

FIG. 2 is a block diagram for explaining a hardware configuration of theMFP 110 according to the first embodiment.

The console unit 111 has a display unit having a touch panel function,various hard keys, or the like, and the console unit 111 displaysinformation to users in accordance with data from a control unit 200,and inputs information into the control unit 200 in accordance withoperation of a user. The scanner unit 112 reads images of originals,generates image data for the images, and supplies the image data to thecontrol unit 200. The printer unit 113 prints images onto sheet (sheetsof paper, etc.) based on the image data received from the control unit200.

The control unit 200 is connecting electrically to the console unit 111,the scanner unit 112, and the printer unit 113, and is connected to theLAN 100 via a network interface (I/F) 206. With this, communication ispossible by a communication protocol such as TCP/IP via the LAN 100. Inthe control unit 200, a CPU 201 is connected to a ROM 202, a RAM 203, anHDD 204, a console unit I/F 205, the network I/F 206, a scanner I/F 207,an image processing unit 208, and a printer I/F 209, through a systembus 211. The CPU 201 executes a boot program in the ROM 202, deploys anOS and control programs stored in the HDD 204 into the RAM 203, andcontrols the MFP 110 comprehensively in accordance with those programs.This control includes execution of programs for realizing the laterdescribed flowcharts. In the ROM 202, the boot program and various dataof the MFP 110 are stored. The RAM 203 provides a work memory for theCPU 201 to operate, and provides an image memory for temporary storageof received image data, or the like. The HDD 204 is a hard disk drive,and stores an OS, various programs, and image data. The console unit I/F205 is an interface unit for connecting the system bus 211 and theconsole unit 111. The network I/F 206 connects the LAN 100 and thesystem bus 211, and performs input/output of information via the network(LAN) 100. The scanner I/F 207 controls an interface between the scannerunit 112 and the control unit 200. The image processing unit 208performs image processing such as rotation, color conversion, and imagecompression/decompression processing on image data input from thescanner unit 112, and image data output to the printer unit 113. Theprinter I/F 209 receives image data processed by the image processingunit 208, and controls printing by the printer unit 113 in accordancewith attribute data attached to the image data. A modem 210 is connectedto the telephone public circuit network 150 and the system bus 211, andperforms transmitting/receiving of facsimiles with an external faxterminal (not shown) via the telephone public circuit network 150. Notethat in the first embodiment, explanation is given for an example of theMFP 110, which is capable of a UI display using the console unit 111,but in place of the MFP 110, for example, an information processingapparatus such as a general-purpose computer, or some other imageprocessing apparatus may be used.

FIG. 3 is a block diagram for showing a hardware configuration of thefile server 120 according to the first embodiment.

The file server 120 comprises a CPU 301, a RAM 302, a ROM 303, an inputunit 304, a network I/F 305, a hard disk drive (HDD) 306, and a displayunit 307, and these are connected communicably to each other via asystem bus 308. The ROM 303 stores a boot program, and upon a poweringon, the CPU 301 reads the boot program, and deploys into the RAM 302 anOS, control programs, or the like, which are installed in the HDD 306.Functions of the file server 120 are realized by the CPU 301 thenexecuting programs deployed into the RAM 302. Also, the CPU 301 performscommunication with other apparatuses on the LAN 100 that are connectedvia the network I/F 305. The input unit 304 includes a keyboard, apointing device, or the like, and accepts instructions from a user. Thedisplay unit 307 performs display of menu screens, messages, or thelike, to the user. Note that the display unit 307 may have a touch panelfunction.

FIG. 4 is a functional block diagram for explaining a software moduleconfiguration of the MFP 110 according to the first embodiment. Thesesoftware modules are installed on the HDD 204 of the MFP 110, and areexecuted under the control of the CPU 201 having been deployed into theRAM 203 upon execution.

A fax reception module 401 performs reception processing when the modem210 receives a facsimile signal. The fax reception module 401 receivesfacsimile data received via the modem 210, converts the facsimile datainto a PDF, or the like, thereby creating a fax document, and saves thefax document as an image file in the HDD 204 by a temporarily storagemodule 403. Also, the fax reception module 401 generates a control fileincluding a received date time, which is a date/time at which the faxreception was performed, a transmission source number which is atelephone number of an external fax terminal (not shown) that sent thefacsimile data via the telephone public circuit network 150. Then, thecontrol file, along with the image file (the fax document) are saved inthe HDD 204. Note, it goes without saying that while the expression “faxdocument” is used in embodiments, generally the fax document may includean image.

A transfer module 402 transfers an image file that the fax receptionmodule 401 saved in the HDD 204 to the file server 120. At this time,the transfer module 402 reads the received date time and thetransmission source number from the control file that the fax receptionmodule 401 saved to the HDD 204 associated with the image file. Also,the transfer module 402 obtains from a transfer setting informationmanagement module 404 transfer setting information which is laterexplained with reference to FIG. 7. Also, the transfer module 402transmits the transmission source number to a destination informationmanagement module 405, and obtains a registered name corresponding tothe transmission source number from the telephone number of destinationinformation, which is explained later with reference to FIG. 6.

FIG. 6 depicts a view for explaining an example of the destinationinformation stored in the destination information management module 405of the MFP 110 according to the first embodiment.

The destination information is something that a user registers inadvance to the destination information management module 405 via theconsole unit 111 of the MFP 110. From column 601 to column 603, andcolumn 607 illustrate columns of data records of row 604 to row 606. Adestination ID in the column 601 is an identifier for uniquelyidentifying a destination. A registered name in the column 602 indicatesa specific user name corresponding to the destination ID. A telephonenumber in the column 603 indicates a transmission source number upon faxreception (a telephone number) corresponding to the registered name. Adestination table name in the column 607 indicates a group of adestination table (an address book) under which the destinationcorresponding to the registered name falls under.

FIG. 7 depicts a view illustrating an example of a file storing transfersetting information stored in the transfer setting informationmanagement module 404 of the MFP 110 according to the first embodiment.

In the file items set on a file server setting screen of FIG. 9, a filenaming rule setting screen of FIG. 10, a folder naming rule settingscreen of FIG. 11, which are explained later, are stored. These settingscreens will be explained in detail later. Note that a format of thesefiles may be CSV, XML, or another format, and the format is irrelevant.

A hostname 701 indicates a host name of the file server 120. In theview, “sharedserver” is designated as the host name of the file server120. Note that an IP address of the file server 120 may be used as thehost name. A folderpath 702 indicates a path that is the starting pointof a storage destination folder of the transferred image file. In thefigure “root” is designated as the storage destination folder path. Ausername 703 indicates a login user's name for authenticating towardsthe file server 120. In FIG. 7, “administrator” which indicates anadministrator is designated as a login user's name. A password 704indicates a password for authenticating towards the file server 120. Inthe figure, “32942xc45” is designated as the password. Note that thecharacter string of the password may be obfuscated using an encryptionmethod such as hashing. A filenamerule 705 indicates a file naming rulefor when saving an image file on the file server 120. A foldernamerule706 indicates a folder path naming rule for when saving an image file onthe file server 120. These will be explained in detail later.

The transfer module 402 generates a file name of the image filetransmitted to the file server 120 based on the filenamerule 705, theregistered name, the telephone number, the received date time, thedestination table name, a line name, a serial number, a random number,or the like. Also, the transfer module 402 generates a folder name forthe image file transmitted to the file server 120 and saved based on thefoldernamerule 706, the registered name, the telephone number, thereception day, and the reception month. Then, the transfer module 402reads an image file saved in the HDD 204, adds the above described filename and folder name to the image file and transmits these to the fileserver 120 designated by the hostname 701. Also, the transfer module 402can perform a later explained transmission test using a telephone numberand a received date time received from a UI module 406, and a faxdocument for testing saved in advance in the HDD 204 by similarprocessing content to the previously explained file transfer processing.

The temporarily storage module 403 receives the control file and theimage file and saves and manages these in the HDD 204. The transfersetting information management module 404 saves and manages in the HDD204 the transfer setting information shown in FIG. 7, for example, whichis set by the UI module 406, which is described later. Also, thetransfer setting information management module 404 transmits savedtransfer setting information to the transfer module 402 in accordancewith a request from the transfer module 402. The destination informationmanagement module 405 saves and manages in the HDD 204 the destinationinformation shown in FIG. 6, for example, which is set by the UI module406, which is described later. The UI module 406 displays variousscreens on the display unit of the console unit 111 via the console unitI/F 205, and detects the content input by the user via the pointingdevice, the hardware keys, or the like, of the console unit 111. Also,the UI module 406 displays a status display screen which is explainedlater with reference to FIG. 8 on the console unit 111, and accepts auser input of whether or not to perform the transfer setting. Also, theUI module 406 displays a file server setting screen which is explainedlater with reference to FIG. 9, obtains file server settings input bythe user, transmits them to the transfer setting information managementmodule 404, and requests saving of the file server settings.Furthermore, the UI module 406 displays on the console unit 111 asetting screen for file naming rules which is later explained withreference to FIG. 10, obtains file naming rules input by the user,transmits them to the transfer setting information management module404, and requests the saving of the file naming rules. Furthermore, theUI module 406 displays on the console unit 111 a setting screen forfolder naming rules which is later explained with reference to FIG. 11,obtains folder naming rules input by the user, transmits them to thetransfer setting information management module 404, and requests thesaving of the folder naming rules. Also, the UI module 406 displays atransmission test screen which is explained later with reference to FIG.12 on the console unit 111, obtains a telephone number of a transmissionsource and a received date time input by the user, transmits these tothe transfer module 402, and requests a transmission test.

FIG. 5 is a functional block diagram for explaining a software moduleconfiguration of the file server 120 according to the first embodiment.These software modules are stored in the HDD 306 of the file server 120,deployed into the RAM 302 upon execution, and executed under the controlof the CPU 301.

A communication module 501 comprises a file transmission service such asSMB (Server Message Block), WebDAV (Web-based Distributed Authoring andVersioning), or the like. The communication module 501 accepts requestsvia the LAN 100, performs processing, and then makes a response with theprocessing result. An authentication module 502 performs authenticationof a client (the MFP 110 here) based on authentication informationincluded in a request to the file transmission service. A filemanagement module 503 performs management of files stored in the HDD 306in accordance with requests to a file transmission service. The filemanagement module 503 saves image files in the HDD 306 in accordancewith folder names and file names received from the MFP 110 via thecommunication module 501, and reads image files. Also, the filemanagement module 503 confirms whether or not a folder of a folder namereceived from the MFP 110 via the communication module 501 exists in theHDD 306. Also, the file management module 503 generates folders in theHDD 306 in accordance with folder names received from the MFP 110 viathe communication module 501.

Next, with reference to FIG. 7, explanation will be given for thefilenamerule 705, which is a file naming rule for when saving an imagefile to the file server 120.

The format of this naming rule is [item name 1] separator (“_” here)[item name 2] separator (“_” here) [item name 3]. For example, whenadding a new item name, a separator “_” and the added item name areadded to the existing naming rule. For example, when further adding“item name 4” in FIG. 7, the naming rule becomes [item name 1]_[itemname 2]_[item name 3]_[item name 4]. Also, the item name[REGISTEREDNAME] corresponds to the registered name in FIG. 6, the itemname [FAXNUMBER] corresponds to the telephone number of FIG. 6, and[DATE] indicates the received date time. Also, while not showngraphically, the item name [ADDRESSTABLENAME] indicates a destinationtable, and the item name [LINENAME] indicates a line name. Also, theitem name [SERIAL] indicates a serial number that the system generates,and more specifically is a number such as [00000001], and a differentserial number is set every time. The item name [RANDOM] indicates arandom number that the system generates, which is a number such as“a761232ed4211cebacd00aa0057b223” for example, and a random number thatis different every time is set. In FIG. 7,[REGISTEREDNAME]_[FAXNUMBER]_[DATE] is designated as the file namingrule, and in such a case the file name becomes [the registered name_thetelephone number(of the transmission source)_the date”.

The foldernamerule 706 indicates a folder path naming rule for whensaving an image file on the file server 120. The format of the namingrule is [item name 1] path separator symbol (“/” here) [item name 2]path separator symbol (“/” here) [item name 3]. When newly adding anitem name, a path separator symbol (“/”) and an added item name areadded to the existing naming rule. For example, in a case where itemname 4 is added, the naming rule for the folder path becomes [item name1]/(path separator symbol)[item name 2]/[item name 3]/[item name 4].Also, the item name [REGISTEREDNAME] indicates a registered name, theitem name [FAXNUMBER] indicates a telephone number, and [DATE] indicatesa received date time. In FIG. 7, [REGISTEREDNAME]/[FAXNUMBER]/[DATE] isdesignated as the naming rule for the folder path, and “registeredname/telephone number/date” is the folder path of the save destination.

FIG. 8 depicts a view illustrating an example of a status display screendisplayed on the console unit 111 of the MFP 110 according to the firstembodiment.

In a status display 801, operation statuses of software modules of FIG.4 which are operating on the MFP 110, and the MFP 110 is displayed. Whenthe UI module 406 performs a display of the status display screen, theUI module 406 confirms the operation statuses of the software module ofthe MFP 110 and the system modules. Then, the UI module 406 displaysthat operation is normal when the software modules of the MFP 110 andthe system modules are operating normally, and displays a status of asoftware module or a module for which a abnormality is occurring when anabnormality is occurring. A “to setting screen” button 802 instructs totransition to a screen for modifying the transfer setting informationmanaged by the transfer setting information management module 404 of theMFP 110. When a user presses (instructs) the “to setting screen (TOSETTING SCREEN) button 802, transfer setting modification processingwhich is explained later with reference to FIG. 13, is activated and thefile server setting modification screen shown in FIG. 9 is transitionedto.

Note that a GUI button for updating the status display 801 in accordancewith the latest statuses of the software module of the MFP 110 and theoperation statuses of the modules of the MFP 110 may be arranged on thestatus display screen shown in FIG. 8.

Also, in the first embodiment, when the “to setting screen” button 802is pressed, transition is made to the file server setting screen of FIG.9, but GUI buttons may be arranged on the status display screen todirectly transition to the screens of FIG. 10, FIG. 11, and FIG. 12which are explained later.

FIG. 9 depicts a view illustrating an example of a file server settingscreen that the MFP 110 according to the first embodiment displays.

A host name input box 901 is an input field for inputting a host name ofthe file server 120 which is a transfer destination of an image file(fax document). A name input into the host name input box 901 istransmitted to the transfer setting information management module 404 bythe UI module 406 of the MFP 110, and saved as the hostname 701 (FIG. 7)of the transfer setting information. A folder path input box 902 is aninput field for inputting a folder name for the file server 120, whichis a transfer destination for an image file. A name input into thisinput box 902 is transmitted to the transfer setting informationmanagement module 404 by the UI module 406 of the MFP 110, and saved asthe folderpath 702 (FIG. 7) of the transfer setting information. A loginuser name input box 903 is an input field for inputting a login user'sname that is necessary for authentication on the file server 120, whichis the transfer destination of the image file. A name input into thisinput box 903 is transmitted to the transfer setting informationmanagement module 404 by the UI module 406 of the MFP 110, and saved asthe username 703 (FIG. 7) of the transfer setting information. A loginpassword input box 904 is an input field for inputting a login passwordthat is necessary for authentication on the file server which is thetransfer destination of the image file. In this input box 904, “*” isdisplayed for input text in order to hide the content that the userinputs. The display of the input text is not limited to “*”, and may beanother symbol such as “+” for example; alternatively the text may bedisplayed without hiding it. The password input in the input box 904 istransmitted to the transfer setting information management module 404 bythe UI module 406 of the MFP 110, and is saved as the password 704 inthe transfer setting information (FIG. 7). A cancel button 905 is abutton for cancelling the modifications on transfer setting informationwith this screen. When a user presses the cancel button 905, a transfersetting modification made via this screen is cancelled, and transitionis made to the status display screen of FIG. 8.

A next button 906 is a button for instructing to modify the settings ofthe file server of the transfer setting information, and to transitionto the later described file naming rule setting screen shown in FIG. 10which is the next screen. When the user presses the next button 906, thefile server settings input on the file server setting screen aretransmitted to the transfer setting information management module 404 bythe UI module 406 of the MFP 110, and the transfer setting managementmodule saves those file server settings. Then the UI module 406transitions to the file naming rule setting screen which is explainedlater with reference to FIG. 10.

Note that in the first embodiment, when the next button 906 is pressed,transition is made to the file naming rule setting screen of FIG. 10,but GUI buttons may be arranged on the file server setting screen inorder to directly transition to the screens of FIG. 11 or FIG. 12.

FIG. 10 depicts a view illustrating an example of a setting screen forsetting a file naming rule that the MFP 110 according to the firstembodiment displays. The file name of the image file that is transferredto the file server 120 is determined in accordance with the file namingrule that the user sets via the file naming rule setting screen.

Items 1002-1004 are areas for designating item names from out ofregistered name, telephone number, received date time, destination tablename, line name, serial number, and random number item names that areused in the file name; here the registered name, the telephone number,and the received date time are selected. Here the item 1002 indicates afirst item name of the file name, the item 1003 indicates a second itemname of the file name, and the item 1004 indicates a third item name ofthe file name. Here the items of the file name can be selected bypull-down menus. As choices in the pull-downs, there are “none”,“registered name”, “fax number”, “date”, “destination table name”, “linename”, “serial number”, and “random number”. Note that “line name” isobtained as the registered name corresponding to the telephone numbershown in FIG. 6, for example, based on a facsimile number designated asa transmission destination. Also, when “none” is selected, it isindicated that none of the item names choices thereafter are generated.For example, when “registered name” is selected for the first item 1002and “none” is selected for the second item 1003, it is determined thatthere is no designation for the second item or items thereafter, and sothe file name becomes simply “registered name”. An item 1005 is apull-down menu for selecting a symbol for a separator which indicatesitem separation; “hyphen”, “underscore”, “space”, or the like, arechoices for separators, and it is possible to select any one of these asthe separator.

A preview display 1006 displays what the file name will be like inaccordance with the selections for the items 1002-1004. The displaycontent of this displays a file name in accordance with the selectionitems according to the selections of the items 1002-1004. In the exampleof FIG. 10, “registered name” is selected for the first item 1002, “faxnumber (telephone number)” is selected for the second item 1003, and“date” is selected for the third item, and underscore “_” is selected asthe separator. Accordingly, the preview display for the file name is“[registered name]_[fax number]_[date]”. A message 1001 is displayedwhen a predetermined condition of selection of any of the received datetime (date), the serial number, or the random number in the items1002-1004 is not satisfied. This is because when none of the receiveddate time (date), the serial number, and the random number is selected,a file name that can be identified uniquely cannot be determined. In theexample of FIG. 10, date is selected in item 1004, but when date is notselected for any of the items 1002-1004, for example, “please select areceived date time” is displayed as the message 1001. Note that in theabove described predetermined condition, it is assumed that the receiveddate time, for example, includes time information up until the secondunit. Also, if information other than this is necessary in order toidentify the file name uniquely, the above described predeterminedcondition may include information other than that described above.

A cancel button 1007 instructs that the content input via the settingscreen be cancelled. When a user presses the cancel button 1007,transition is made to the status display screen shown in FIG. 8, forexample. A return button 1008 instructs that the previous screen bereturned to. When the user presses the return button 1008, transition ismade to a file server setting screen shown in FIG. 9, for example. Anext button 1009 instructs that the next screen be proceeded to. Whenthe user presses the next button 1009, transition is made to a foldernaming rule setting screen shown in FIG. 11, for example.

Note that the next button 1009 becomes press able when any of the date,the serial number, or the random number is selected in the items1002-1004. When none of the items is selected, the next button 1009cannot be selected, and the next button 1009 cannot be pressed. Withthis, a file name being generated in accordance with a naming rule bywhich the file name is not unique can be suppressed.

FIG. 11 depicts a view illustrating an example of a setting screen forsetting a folder naming rule that the MFP 110 according to the firstembodiment displays. The folder name of a file saved to the file server120 is determined in accordance with the folder naming rule set on thisscreen.

A check box 1101 is a check-box for allowing a user to select whether ornot to save an image file dividing into layers. When the check box 1101is checked, the folder name is generated by the naming rule set on thisscreen, and the image file is saved therein. When the check box 1101 isnot checked, the image file is saved directly below the folder pathdesignated by the file server setting screen shown in FIG. 9.

Items 1102-1104 show layer names. Here a first layer 1102, a secondlayer 1103, and a third layer 1104 of the folder are included. Here thefolder names corresponding to each level can be selected by pull-downmenus 1105-1107. As choices in the pull-downs, “none”, “registeredname”, “fax number”, “reception day”, “reception month”, “destinationtable name”, “line name” are included. Also, when “none” is selected, itis indicated that none of the layers of the choices thereafter aregenerated. For example, when “registered name” is selected for the firstlayer 1102 and “none” is selected for the second layer 1103, it isdetermined that there is no designation for the folder name of thesecond layer or items thereafter, and so the folder name becomes simply“registered name”. A preview display 1108 shows a preview display of thefolder name in accordance with the selection results for the items1102-1104. In the example of FIG. 11, “registered name” is selected forthe first layer 1102, “fax number” is selected for the second layer1103, and “reception day” is selected for the third layer 1104, and sothe preview display 1108 is “[registered name]/[fax number]/[receptionday]”.

A cancel button 1109 instructs that the user operation input via thesetting screen be cancelled. When a user presses the cancel button 1109,transition is made to the status display screen shown in FIG. 8, forexample. A return button 1110 instructs that the previous screen bereturned to. When the user presses the return button 1110, transition ismade to a file naming rule setting screen shown in FIG. 10, for example.A next button 1111 instructs that the next screen be proceeded to. Whenthe user presses the next button 1111, transition is made to thetransmission test screen shown in FIG. 12, for example.

FIG. 12 depicts a view illustrating an example of a transmission testscreen that the MFP 110 according to the first embodiment displays.

A transmission source number input box 1201 is an input field forinputting information used as a transmission source telephone numberwhen performing a transmission test. A telephone number input into thetransmission source number input box 1201 is transmitted to the transfermodule 402 by the UI module 406 of the MFP 110 and is used as atransmission source number (telephone number) upon a transmission test.A received date time input box 1202 is an input field for inputting adate/time used as the received date time for when performing atransmission test. A date/time input into the received date time inputbox 1202 is transmitted to the transfer module 402 by the UI module 406of the MFP 110, and used as the received date time upon a transmissiontest.

A setting confirmation button 1203 is a button for transitioning to asetting confirmation screen (not shown) for displaying transfer settinginformation input via the setting screens of FIG. 9, FIG. 10, and FIG.11. When the user presses the setting confirmation button 1203, asetting confirmation screen for displaying transfer setting informationinput via screens as shown in FIG. 9, FIG. 10, and FIG. 11 is displayedby the UI module 406 of the MFP 110. A transmission test button 1204 isa button for instructing so that a transmission test is performed usingthe transfer setting information input via screens as shown in FIG. 9,FIG. 10, and FIG. 11, and information input by the transmission sourcenumber input box 1201 and the received date time input box 1202. Whenthe user presses the transmission test button 1204, the UI module 406 ofthe MFP 110 transmits the telephone number of the transmission sourcenumber input box 1201 and the date/time of the received date time inputbox 1202 to the transfer module 402, and a transmission test request istransmitted to the transfer module 402. The transfer module 402 performsa test transmission to the file server 120 which assumes that a faxdocument is received at a date/time and a transmission source numberreceived when the transmission test button 1204 is pressed. The transfermodule 402 displays a transmission test result screen (not shown) fordisplaying the result of the test transmission when the testtransmission completes.

A cancel button 1205 is a button for cancelling the transfer settinginformation settings. When a user presses the cancel button 1205,transition is made to the status display screen shown in FIG. 8, forexample. A return button 1206 is a button for transitioning to theprevious screen. When the user presses the return button 1206,transition is made to the folder naming rule setting screen of FIG. 11,which is the previous screen. An OK button 1207 is a button forcompleting the setting of the transfer setting information, andtransitioning to the status display screen shown in FIG. 8. When theuser presses the OK button 1207, the UI module 406 of the MFP 110transitions to the status display screen shown in FIG. 8.

Note that in the first embodiment, a transmission source number usedupon testing is input by the transmission source number input box 1201,and the received date time is input by the received date time input box1202. However, an input box, an input button, or the like, may bearranged in order to designate a fax document used for anothertransmission test.

FIG. 13 is a flowchart for describing file server setting, and filenaming rule and folder naming rule setting processing by the MFP 110according to the first embodiment. Note that the operations (steps)shown in this flowchart are realized by the CPU 201 of the MFP 110deploying a control program stored in the HDD 204 into the RAM 203, andexecuting the control program. Also, this flowchart is executed when auser selects a control program that executes this flowchart via theconsole unit 111 of the MFP 110.

Firstly, in step 51301, the CPU 201 displays a status display screensuch as the one shown in FIG. 8, for example. Next, the processingproceeds to step S1302, and the CPU 201 determines whether or not the“to setting screen” button 802 is pressed on the status display screen.If the “to setting screen” button 802 is pressed, the processingproceeds to step S1303, and the CPU 201 displays the file server settingscreen shown in FIG. 9, for example. Then the user inputs a name, a pathof a folder, or the like, of a file server which is a transferdestination, authentication information, or the like, via the fileserver setting screen.

Next, the processing proceeds to step S1304, the CPU 201 determineswhether the user pressed the cancel button 905 or the next button 906 onthe file server setting screen. When it is determined that the nextbutton 906 is pressed, the processing proceeds to step S1305, and whenit is determined that the cancel button 905 is pressed, the informationset on this screen is cancelled, and the processing returns to stepS1301. In step S1305, the CPU 201 stores setting information of the fileserver input via the file server setting screen into the HDD 204 of theMFP 110.

Next, the processing proceeds to step S1306, and the CPU 201 displays afile naming rule setting screen, such as the one shown in FIG. 10, forexample. Then, the user inputs the file naming rule setting informationvia this setting screen, and file naming rule setting processing isexecuted. Next, the processing proceeds to step S1307, and the CPU 201determines which button the user pressed on the file naming rule settingscreen. When a button is not pressed, steps S1306 and S1307 areexecuted. In step S1307, when it is determined that the next button 1009is pressed, the processing proceeds to step S1308, but as previouslyexplained, there are cases in which the next button 1009 cannot bepressed. The file naming rule setting processing will be explained laterwith reference to FIG. 18. Meanwhile, if it is determined that thecancel button 1007 is pressed, the information set on this screen iscancelled, and the processing proceeds to step S1301, and if it isdetermined that the return button 1008 is pressed, the processingproceeds to step S1303, and, for example, the file server setting screenshown in FIG. 9 is displayed.

FIG. 18 is a flowchart for describing file naming rule settingprocessing of step S1306 in FIG. 13.

Firstly, in step S1801, the CPU 201 obtains information selected by theitems 1002-1004 of the setting screen of the file naming rule shown inFIG. 10, for example. Next, the processing proceeds to step S1802, andthe CPU 201 determines whether or not at least one of items by which afile name can be set uniquely is selected based on the informationobtained in step S1801. Note that the items for which the file name willbecome unique are, as previously explained, “date”, “serial number”, and“random number”, and it is determined whether or not one or more ofthese items is included. Then, if one or more of the items for which thename will be unique is included, it is determined that an item by whichthe file name can be set uniquely is selected, the processing proceedsto step S1805. In step S1805, the CPU 201 stores the file naming ruledetermined on this screen in the HDD 204.

Meanwhile, if, in step S1802, the CPU 201 determines that an item bywhich the file name will be unique is not included, the processingproceeds to step S1803. In step S1803, the CPU 201 displays a warningmessage prompting the user to select an item by which the file name willbe unique in the message 1001 of FIG. 10. In FIG. 10, “Please select areceived date time” is displayed as the message 1001, but a message maybe displayed to cause another item by which the file name will be uniqueto be selected.

Next, the processing proceeds to step S1804, and the CPU 201 sets sothat the user cannot press the next button 1009. More specifically, theCPU 201 sets a state in which the next button 1009 is displayed to begrayed out and disabled (the button cannot be pressed), so that the nextscreen cannot be transitioned to. By doing this, it is possible toprevent a non-unique file name being added for an image file. In thisway, when the file name is designated in a way in which it will beunique on the file naming rule setting screen, the next button 1009 canbe pressed, and when the user presses the next button 1009, theprocessing proceeds to step S1308 (FIG. 13).

Next, in step S1308, the CPU 201 displays a folder naming rule settingscreen, such as the one shown in FIG. 11, for example. Then, the userinputs the folder naming rule setting information via this settingscreen, and folder naming rule setting processing is executed. Next, theprocessing proceeds to step S1310, and the CPU 201 determines whichbutton the user pressed on the folder naming rule setting screen. When abutton is not pressed, steps S1309 and S1310 are executed. If it isdetermined that the user presses the next button 1111 in step S1310, theprocessing proceeds to step S1311. If the user presses the cancel button1109, the information set on the screen is cancelled and the processingproceeds to step S1301, and if the user presses the return button 1110,the processing proceeds to step S1306, and for example, the file namingrule setting screen shown in FIG. 10 is displayed. In step S1311, theCPU 201 stores in the HDD 204 the information that the user input on thefolder naming rule setting screen, for example.

Next, the processing proceeds to step S1312, and the CPU 201 displaysthe transmission test screen shown in FIG. 12, for example. Next, theprocessing proceeds to step S1313, and the CPU 201 determines whichbutton the user pressed on the transmission test screen. Here, if theuser did not press any button, steps S1312 and S1313 are executed. If itis determined that the user pressed the OK button 1207, the processingcompletes. Meanwhile, if it is determined that the user pressed thecancel button 1205, the information set on this screen is cancelled, andthe processing proceeds to step S1301. Also, if it is determined thatthe return button 1206 is pressed, the processing proceeds to stepS1309, and the folder naming rule setting screen shown in FIG. 11, forexample, is displayed. Furthermore, if it is determined that the userpressed the transmission test button 1204, the processing proceeds tostep S1314. In step S1314, the CPU 201 executes a transmission testbased on the content set in the file server setting screen (FIG. 9), thefile naming rule setting screen (FIG. 10), the folder naming rulesetting screen (FIG. 11), and the transmission test screen (FIG. 12),and the processing proceeds to step S1312.

Next, explanation will be given for fax reception processing by the MFP110 according to the first embodiment. Below, explanation is givenfocusing on processing in which the MFP 110 receives a fax document, andtransfers the fax document as an image file. Here, using previouslyexplained transfer setting information (FIG. 7), and destinationinformation (FIG. 6), the received fax document is transferred as animage file to the file server 120. At this time, the file name and thefolder name of the fax document (image file) are generated andtransferred to the file server 120. Note that the destinationinformation is already registered to the destination informationmanagement module 405 by the user in advance via the console unit 111 ofthe MFP 110 as shown in FIG. 6. Here, an explanation of processing forregistering the destination information is omitted.

FIG. 14 is a sequence diagram for explaining processing in which the MFP110 according to the first embodiment receives image data (documentdata) in a fax, and transfers an image file of the image data that isreceived to the file server 120.

A fax image is sent from an external fax terminal to the MFP 110 at1401. When the MFP 110 receives the fax image, the fax reception module401 and the transfer module 402 perform fax reception processing.

FIG. 15 is a flowchart for describing fax reception processing by theMFP 110 according to the first embodiment. Note that the operations(steps) shown in this flowchart are realized by the CPU 201 of the MFP110 deploying a control program stored in the HDD 204 into the RAM 203,and executing the control program.

Firstly, in step S1501 the CPU 201 uses the modem 210 to receive afacsimile signal from an external fax terminal via the public switchedtelephone network 150. Also, the CPU 201 obtains a telephone number ofthe external fax terminal as a transmission source number using themodem 210, and further obtains a date/time at which the fax reception isperformed as the received date time. Next, the processing proceeds tostep S1502, and the CPU 201 converts the fax document received in stepS1501 into an image file such as a PDF. Also, the CPU 201 generates acontrol file in which the telephone number of the transmission sourceand the received date time obtained in step S1501 are recited. Then, theCPU 201 temporarily stores an image file including the fax document inthe HDD 204 along with the control file.

Next, the processing proceeds to step S1503, and the CPU 201 determineswhether or not the temporary storing of the image file to the HDD 204succeeded. If it was able to store the image file, the processingproceeds to step S1504, and the CPU 201 obtains the transmission sourcetelephone number, the received date time, or the like, storedtemporarily on the HDD 204. Meanwhile, when the temporary storing of theimage file failed, error processing is performed, and the processingcompletes. An example of when the temporary storing fails is a case thatthere is insufficient capacity in the HDD 204. Also, in the errorprocessing here, together with causing the printer unit 113 to print thefax document by transmitting it to the printer unit 113 via the printerI/F 209, an error status is caused to be displayed by displaying thestatus display screen (FIG. 8) on the console unit 111.

Next, the processing proceeds to step S1505, and the CPU 201 generates afile name in order to transfer the image file to the file server 120referencing the transmission source number and the received date timeobtained in step S1504, the transfer setting information (FIG. 7), andthe destination information (FIG. 6). Explanation is given withreference to the flowchart of FIG. 16 for details of processing of stepS1505.

FIG. 16 is a flowchart for describing file name generation processing instep S1505 of FIG. 15 for an image file to be transferred. Note that theoperations shown in this flowchart are realized by the CPU 201 of theMFP 110 deploying a control program stored in the HDD 204 into the RAM203 and executing the control program, and the performer of theseoperations is explained as the CPU 201.

Firstly, in step S1601, the CPU 201 obtains the filenamerule 705 (filenaming rule) saved in the HDD 204. Next, the processing proceeds to stepS1602, and the CPU 201 obtains destination information (FIG. 6) based onthe telephone number. Here, the destination information is obtained bysearching the registered name with the telephone number as a key. Next,the processing proceeds to step S1603, and the CPU 201 determineswhether or not the registered name corresponding to the telephone numberexists. If the registered name exists, the processing proceeds to stepS1604, the CPU 201 obtains the corresponding registered name, and theprocessing proceeds to step S1606. On the other hand, if the registeredname does not exist, the processing proceeds to step S1605, and the CPU201 obtains a default registered name set in advance, and the processingproceeds to step S1606. Note, an example of the default registered nameis when “not available”, or the like, is set. Also, the defaultregistered name may be saved in advance in the ROM 202 or the HDD 204.Also, configuration may be taken such that an input box for setting thedefault registered name is arranged on the file naming rule settingscreen of FIG. 10, for example, and the user is able to modify thedefault name. In step S1606, the CPU 201 generates a file name using theregistered name, the telephone number of the transmission source, thereceived date time, the destination table name, the line name, and thelike, in accordance with the file naming rule obtained in step S1601.

Then, the processing proceeds to step S1506 of FIG. 15. In step S1506,the CPU 201 generates the folder name for transferring based on thetelephone number of the transmission source and the received date timeobtained in step S1504, the transfer setting information (FIG. 7) andthe destination information (FIG. 6). Explanation is given withreference to the flowchart of FIG. 17 for details of processing of stepS1506.

FIG. 17 is a flowchart for describing folder name generation processingin step S1506 of FIG. 15 of the file server 120 on which the image filetransferred is stored. Note that the operations shown in this flowchartare realized by the CPU 201 of the MFP 110 deploying a control programstored in the HDD 204 into the RAM 203 and executing the controlprogram, and the performer of these operations is explained as the CPU201.

Firstly, in step S1701, the CPU 201 obtains the foldernamerule 706 savedin the HDD 204. Next, the processing proceeds to step S1702, and the CPU201 obtains destination information, and obtains the correspondingregistered name by searching for it using the telephone number obtainedin step S1504 as the key. Then, the processing proceeds to step S1703,and the CPU 201 determines whether or not a registered namecorresponding to the telephone number exists. If it is determined thatit does exist, the processing proceeds to step S1704, and the CPU 201obtains the corresponding registered name, and the processing proceedsto step S1706. Meanwhile, in step S1703, if it is determined that theregistered name corresponding to the telephone number does not exist,the processing proceeds to step S1705, and the CPU 201 obtains thedefault registered name set in advance, and the processing proceeds tostep S1706. Note, an example of the default registered name is when “notavailable”, or the like, is set. Also, the default registered name maybe saved in advance in the ROM 202 or the HDD 204. Also, configurationmay be taken such that an input box for setting the default registeredname is arranged on the folder naming rule setting screen of FIG. 11,for example, and so that a user is able to modify the default name savedin the HDD 204 by user input.

In step S1706, the CPU 201 generates a folder name using the registeredname, the telephone number of the transmission source, and the receiveddate time in accordance with the foldernamerule 706 obtained in stepS1701. Then, the processing proceeds to step S1707, and the CPU 201 setsthe folder path to the head of the folder name, and the processingcompletes.

Next, once again the explanation returns to FIG. 14, and the MFP 110performs authentication processing on the file server 120 at 1402. Thisauthentication processing is executed from step S1507 of FIG. 15.

In step S1507 of FIG. 15, the CPU 201 reads the transfer settinginformation (FIG. 7) from the HDD 204, and obtains the hostname 701, theusername 703, and the password 704. Then, the CPU 201 accesses theaddress designated by the hostname 701, and transmits the username 703and the password 704 to the file server 120 along with theauthentication request as the user name and the password respectively.Then, the processing proceeds to step S1508 of FIG. 15.

Once again, the explanation returns to FIG. 14. When the communicationmodule 501 of the file server 120 receives an authentication requestfrom the MFP 110 at 1402, the communication module 501 obtains the username and the password from the authentication request and transmits themto the authentication module 502. The authentication module 502 performsa verification of the user ID and the password using authenticationinformation saved in the HDD 306, and transmits the result of theauthentication to the communication module 501. With this, thecommunication module 501 transmits the received authentication result tothe MFP 110.

In step S1508 of FIG. 15, the CPU 201 determines whether or not theauthentication result is received from the file server 120. When it isdetermined that the authentication result is not received, step S1508 isexecuted, and when the authentication result is received, the processingproceeds to step S1509, and the CPU 201 determines whether or not theauthentication result received in step S1508 is an authenticationsuccess. If the CPU 201 determines that it is an authentication success,the processing proceeds to step S1510, and if that is not the case,error processing is performed, and the processing completes. In thiserror processing, a status display screen (FIG. 8) is displayed on theconsole unit 111, causing an error status to be displayed.

If the MFP 110 succeeds at authentication at 1402 in FIG. 14, then at1403, the MFP 110 makes a query as to whether or not a folder of thefolder name generated in step S1506 exists on the file server 120 and ifno such folder exists in the file server 120, the MFP 110 requests forthe file server 120 to generate the folder. Here, the MFP 110 executesthe processing of step S1510 of FIG. 15.

In step S1510, the CPU 201 transmits the folder name generated in stepS1506 to the file server 120, and transmits an existence confirmationrequest for a file of the folder name.

Then, when, at 1403 of FIG. 14, the communication module 501 of the fileserver 120 receives an existence confirmation request for the folderfrom the MFP 110, the communication module 501 transmits the folder nameincluded in the folder existence confirmation request to the filemanagement module 503, requesting folder existence confirmationprocessing. With this, the file management module 503 determines whetheror not the folder of the received folder name exists in the HDD 306, andtransmits the confirmation result to the communication module 501 as thefolder existence confirmation result. With this, the communicationmodule 501 transmits the folder existence confirmation result to the MFP110. Then, the processing proceeds to step S1511 of FIG. 15.

In step S1511, the CPU 201 determines whether or not the folderexistence confirmation result was received from the file server 120. Ifit is determined that the folder existence confirmation is not received,once again the processing proceeds to step S1511. If, in step S1511, itis determined that the folder existence confirmation is received, theprocessing proceeds to step S1512. In step S1512, the CPU 201 determineswhether or not the folder of the folder name generated in step S1506exists on the file server 120 from the folder existence confirmationreceived in step S1511. Here, if it is determined that a folder of thesame name exists, the processing proceeds to step S1515, and if it isdetermined that a folder of the same name does not exist, the processingproceeds to step S1513.

In step S1513, the CPU 201 transmits the folder name generated in stepS1506 to the file server 120, thereby performing a folder generationrequest. Once again, the explanation returns to FIG. 14, and when, at1403, the communication module 501 of the file server 120 receives thefolder generation request from the MFP 110, the communication module 501transmits the folder name included in the folder generation request tothe file management module 503, requesting the generation of the folderof the folder name. The file management module 503 generates the folderof the received folder name in the HDD 306, and transmits a responsethat it was generated to the communication module 501. When thecommunication module 501 receives the folder generated response, thecommunication module 501 transmits a folder generated response to theMFP 110.

In step S1514, the CPU 201 determines whether or not the foldergenerated response is received from the file server 120. If the foldergenerated response is not received, step S1514 is executed, and if thefolder generated response is received, the processing proceeds to stepS1515. In step S1515, the CPU 201 reads the fax document stored on theHDD 204, and transmits the fax document along with the file namegenerated in step S1505 and the folder name generated in step S1506 tothe file server 120, thereby transmitting a file save request.

This corresponds to reference numeral 1404 of FIG. 14. At 1404, the MFP110 transmits a fax document (image file), designating the file namegenerated in step S1505, and the folder name generated in step S1506 tothe file server 120. When, in this way, the communication module 501 ofthe file server 120 receives the file save request, the communicationmodule 501 obtains the file, the folder name, and the file name from thefile save request. Then, the communication module 501 transmits theobtained file, folder name, and file name to the file management module503, and requests storage of the designated folder name and file name.The file management module 503 stores the received file in a designatedlocation at the folder name and the file name in the HDD 306, andtransmits a storage response to the communication module 501. Thecommunication module 501 transmits the storage response to the MFP 110as a file transmission response.

In this way, the CPU 201 determines whether or not the file transmissionresponse is received from the file server 120 in step S1516 of FIG. 15.If the file transmission response is not received, the processing onceagain proceeds to step S1516, and if the file transmission response isreceived, the processing completes.

By virtue of the above explained processing, when the MFP 110 receives afax, the MFP 110 generates a file name for the received image file (faxdocument) in accordance with a file naming rule of the transfer settinginformation, a transmission source number, a received date time, and aregistered name of destination information corresponding to thetransmission source number. Also, the MFP 110 generates a folder name inaccordance with a folder path and a folder naming rule of the transfersetting information, a transmission source number, a received date time,and a registered name, and the like, of destination informationcorresponding to a transmission source number. Also, the MFP 110performs an existence confirmation for the folder that is to begenerated towards the file server 120, and if the same folder does notexist on the file server 120, the image file is stored at the locationof the generated folder name with the file name having performed afolder generation request.

By the first embodiment, as explained above, by setting a file namingrule and a folder naming rule in advance, it is possible to store animage file received in a fax in a desired folder on a file server byadding a desired file name to the image file. Also for the file namingrule and the folder naming rule, it is possible to search fordestination information using a telephone number of the transmissionsource of a received fax, and to obtain and use a registered namecorresponding to the destination information. Also, in the file namingrule, it is possible to set a separator as a separation of the items.Furthermore, in the file naming rule, it is possible for the user toselect items such that the file name will become unique in a format thatthe user can recognize. With this, it is possible to increase file namesetting flexibility and to improve work efficiency for the user.

Also, because it is possible to generate a desired folder on the fileserver on which the image file is saved, there is the effect that theeffort of the user searching for the desired image file can be reduced.

Second Embodiment

Next, explanation will be given for a second embodiment of the presentinvention. In the second embodiment, explanation is given for an examplein which file name setting processing control that is different fromthat of the previously described first embodiment is performed. In thesecond embodiment, a naming rule is saved without executing item checkprocessing (step S1802) in the file naming rule setting processing ofFIG. 18.

FIG. 19 depicts a view illustrating an example of a confirmation dialogdisplayed by the MFP 110 according to the second embodiment of thepresent invention. Note that the configurations of the MFP 110 and thefile server 120, and the system configuration according to the secondembodiment, are the same as those in the previously described firstembodiment, and so explanation thereof will be omitted.

A message 1901 shows a message displayed in this confirmation dialog. AYES button 1902 is pressed when a user acknowledges display content inthis confirmation dialog. If the user presses the YES button 1902,transition is made to the previously explained folder naming rulesetting screen shown in FIG. 11, for example. A NO button 1903 isdesignated when a user does not acknowledge display content in thisconfirmation dialog. If the user presses the NO button 1903, transitionis made to the file naming rule setting screen of FIG. 10, for example.

FIG. 20 is a flowchart for describing confirmation dialog displayprocessing by the MFP 110 according to the second embodiment. Note thatthe operations shown in this flowchart are realized by the CPU 201 ofthe MFP 110 deploying a control program stored in the HDD 204 into theRAM 203 and executing the control program, and the performer of theseoperations is explained as the CPU 201. The processing illustrated bythe flowchart is executed when the folder naming rule setting screen isdisplayed in step S1309 of FIG. 13.

Firstly, in step S2001, the CPU 201 obtains information of thefilenamerule 705 saved in the transfer setting information (FIG. 7).Next, the processing proceeds to step S2002, and the CPU 201 determineswhether or not the display condition of the confirmation dialog issatisfied based on the naming rule obtained in step S2001. Hereexplanation will be given for details of the display condition for theconfirmation dialog using transfer setting information.

FIG. 21 depicts a view illustrating an example of transfer settinginformation according to the second embodiment. In FIG. 21, referencenumerals 2101-2106 are the same as the transfer setting informationitems 701-706 of FIG. 7 in accordance with the previously describedfirst embodiment, and so explanation thereof will be omitted.

A dialogrule 2107 shows a condition for displaying the confirmationdialog. This condition is designated when a confirmation dialog displaysetting screen (not shown) for designating the condition is displayedvia the UI module 406, or when a Web browser displaying a confirmationdialog display setting screen (not shown) for designating the condition.In the dialogrule 2107, it is possible to designate “registered name”,“fax number”, “date”, “destination table name”, “line name”, “serialnumber”, “random number” or the like. In FIG. 21, [REGISTEREDNAME](registered name) and [FAXNUMBER] (fax number) are designated, and ifthese are not included in the filenamerule 2105, a confirmation dialogmatching the above-described condition is displayed.

If, in step S2002 of FIG. 20, the CPU 201 determines that the displaycondition of the confirmation dialog is satisfied, the processingproceeds to step S2003, a confirmation dialog as shown in FIG. 19, forexample, is displayed, and the processing completes. Meanwhile, if, instep S2002, the CPU 201 determines that the display condition is notsatisfied, the processing completes without displaying the confirmationdialog.

By the second embodiment, as explained above, it is possible to arrangerestrictions of later processing (displaying the confirmation dialog inthe second embodiment) by designating a particular condition.Accordingly, by setting conditions that are confirmed by the user inaccordance with the cooperating system and apparatus, for example, it ispossible to improve the convenience of the user because it is possibleto execute processing in accordance with the system or the apparatus.

Third Embodiment

In the previously described first embodiment, the folder naming rule isset via the folder naming rule setting screen shown in FIG. 11, forexample. In the third embodiment, explanation is given for an example inwhich the folder naming rule is set via a setting screen that isdifferent to that of the previously described first embodiment. Notethat the configurations of the MFP 110 and the file server 120, and thesystem configuration according to the third embodiment, are the same asthose in the previously described first embodiment, and so explanationthereof will be omitted.

FIG. 22 depicts a view illustrating an example of a folder naming rulesetting screen displayed by the MFP 110 according to the thirdembodiment of the present invention. This screen is displayed as thefolder naming rule setting screen displayed to the console unit 111 instep S1306 of FIG. 13, and the folder name is determined whentransferring to the file server 120 in accordance with the folder namingrule set on this screen.

Reference numerals 2201-2203 of FIG. 22 show folder naming rule choices,and the one naming rule that is checked amongst these is applied as thefolder naming rule. When a naming rule 2201 is selected, the folder namecomprising “registered name/fax number/date” is generated. When a namingrule 2202 is selected, the folder name comprising “date/registeredname/fax number” is generated. Also, when a naming rule 2203 isselected, a folder name comprising “fax number/registered name/date” isgenerated.

A cancel button 2204 indicates that the processing via this screen becancelled. When a user presses the cancel button 2204, transition ismade to the status display screen shown in FIG. 8, for example. A returnbutton 2205 instructs that the previous screen be returned to. When theuser presses the return button 2205, transition is made to the filenaming rule setting screen shown in FIG. 10, for example. Also, a nextbutton 2206 indicates that the next screen be proceeded to. If the userpresses the next button 2206, transition is made to the transmissiontest screen shown in FIG. 12, for example.

The folder naming rule setting screen shown in FIG. 19 is used in placeof the folder naming rule setting screen of FIG. 11 in the firstembodiment in the transfer setting processing shown in the flowchart ofpreviously explained FIG. 13. Then, in step S1309, the folder namingrule setting screen shown in FIG. 22 is displayed. Then, in step S1310,it is determined which button the user pressed in the folder naming rulesetting screen. If the user presses the next button 2206, the processingproceeds to step S1311. If the user presses the cancel button 2204, theprocessing proceeds to step S1301. If the user presses the return button2205, the processing proceeds to step S1306. In step S1311, the CPU 201stores the information input on the folder naming rule setting screen ofFIG. 22 to the HDD 204.

As explained above, by virtue of the third embodiment, it is possible toachieve the same effect as in the first embodiment. Also there is theeffect that the operation of the user becomes simpler because, uponsetting the folder name, it is possible for the user to set a desirednaming rule by selecting the naming rule from out of folder naming rulesdetermined in advance. With this, it is possible to more simply set thefolder in which to store the received fax document.

Other Embodiments

In the first embodiment, it is possible to designate the registeredname, the telephone number, and the date as the folder name, butconfiguration may be taken such that, for example, it is possible todesignate a line number as the folder name in a case where there are twofax line connections to the modem 210 of the MFP 110.

In the above-described first through third embodiments, setting isperformed using a plurality of screens in which setting screens are in awizard format, but configuration may be taken such that everything canbe set on a single screen.

Also, in the above-described first through third embodiments, bydisplaying setting screens on the console unit 111, the user is allowedto operate by controlling the console unit 111 of the MFP 110, butconfiguration may be taken such that it is possible to operate thesetting screen from a Web browser on a general-purpose personalcomputer.

Embodiments of the present invention can also be realized by a computerof a system or apparatus that reads out and executes computer executableinstructions (e.g., one or more programs) recorded on a storage medium(which may also be referred to more fully as a ‘non-transitorycomputer-readable storage medium’) to perform the functions of one ormore of the above-described embodiment(s) and/or that includes one ormore circuits (e.g., application specific integrated circuit (ASIC)) forperforming the functions of one or more of the above-describedembodiment(s), and by a method performed by the computer of the systemor apparatus by, for example, reading out and executing the computerexecutable instructions from the storage medium to perform the functionsof one or more of the above-described embodiment(s) and/or controllingthe one or more circuits to perform the functions of one or more of theabove-described embodiment(s). The computer may comprise one or moreprocessors (e.g., central processing unit (CPU), micro processing unit(MPU)) and may include a network of separate computers or separateprocessors to read out and execute the computer executable instructions.The computer executable instructions may be provided to the computer,for example, from a network or the storage medium. The storage mediummay include, for example, one or more of a hard disk, a random-accessmemory (RAM), a read only memory (ROM), a storage of distributedcomputing systems, an optical disk (such as a compact disc (CD), digitalversatile disc (DVD), or Blu-ray Disc (BD)™), a flash memory device, amemory card, and the like.

While the present invention has been described with reference toexemplary embodiments, it is to be understood that the invention is notlimited to the disclosed exemplary embodiments. The scope of thefollowing claims is to be accorded the broadest interpretation so as toencompass all such modifications and equivalent structures andfunctions.

This application claims the benefit of Japanese Patent Application No.2014-174285, filed Aug. 28, 2014, which is hereby incorporated byreference herein in its entirety.

What is claimed is:
 1. An information processing apparatus, comprising:a first setting unit configured to set a naming rule for an image file;a determination unit configured to determine whether or not the namingrule set by the first setting unit satisfies a predetermined condition;a warning unit configured to warn a user if it is determined by thedetermination unit that the naming rule does not satisfy thepredetermined condition; and a control unit configured to control so asto, if it is determined by the determination unit that the naming rulesatisfies the predetermined condition, generate a file name of the imagefile in accordance with the naming rule set by the first setting unit,and store the image file.
 2. The information processing apparatusaccording to claim 1, wherein the image file is generated based on imagedata that is received, and wherein the first setting unit comprises: afirst selection unit configured to allow a user to select as an item ofthe naming rule for the image file at least one of a received date timeof the image data, destination information of a transmission source, aline name, a serial number, and a random number; and a separator settingunit configured to set a separator indicating a separation of the itemselected by the first selection unit.
 3. The information processingapparatus according to claim 2, wherein the predetermined condition isthat the naming rule includes at least one of the received date time,the serial number and the random number.
 4. The information processingapparatus according to claim 1, wherein the control unit controls sothat the image file and the file name are transmitted to a server andstored.
 5. The information processing apparatus according to claim 1,further comprising a second setting unit configured to set a naming rulefor a folder in which to store the image file.
 6. The informationprocessing apparatus according to claim 5, wherein the image file isgenerated based on image data that is received, and wherein the secondsetting unit comprises: a second selection unit configured to allow auser to select at least one of a received date time of the image dataand destination information of a transmission source as an item of thenaming rule for the folder; and a layer setting unit configured to setthe item selected by the second selection unit in a layer.
 7. Theinformation processing apparatus according to claim 5, wherein thecontrol unit controls so that a folder name of a folder in which tostore the image file is further generated in accordance with the namingrule for the folder set by the second setting unit, and the image file,the file name, and the folder name are transmitted to a server andstored.
 8. The information processing apparatus according to claim 5,wherein the second setting unit sets the naming rule of the folder byallowing a user to select a predetermined set of items of the namingrule for the folder.
 9. A method of controlling an informationprocessing apparatus operable to store an image file, the methodcomprising: setting a naming rule for an image file; determining whetheror not the naming rule set in the setting satisfies a predeterminedcondition; warning a user if it is determined in the determining thatthe naming rule does not satisfy the predetermined condition; andcontrolling so as to, if it is determined in the determining that thenaming rule satisfies the predetermined condition, generate a file nameof the image file in accordance with the naming rule set in the setting,and store the image file.
 10. A non-transitory computer-readable storagemedium storing a program for causing a computer to function as aninformation processing apparatus comprising: a first setting unitconfigured to set a naming rule for an image file; a determination unitconfigured to determine whether or not the naming rule set by the firstsetting unit satisfies a predetermined condition; a warning unitconfigured to warn a user if it is determined by the determination unitthat the naming rule does not satisfy the predetermined condition; and acontrol unit configured to control so as to, if it is determined by thedetermination unit that the naming rule satisfies the predeterminedcondition, generate a file name of the image file in accordance with thenaming rule set by the first setting unit, and store the image file.